Closes NousResearch#14

LangChain's `_parse_python_function_docstring` expects docstrings to
follow the Google Python style guide in order to correctly extract
function descriptions and parameter metadata for OpenAI tool schemas.

The existing docstrings in `functions.py` had several formatting issues
that caused `convert_to_openai_tool` to produce malformed tool
definitions:

1. Missing 4-space indentation under Args/Returns sections
   (get_financial_statements, get_key_financial_ratios,
   get_analyst_recommendations, get_dividend_data, get_company_news,
   get_technical_indicators, get_company_profile)

2. Inconsistent 2-space indentation instead of 4-space
   (get_current_stock_price)

3. Note section leaking into tool description
   (code_interpreter)

4. Detailed Keys block under Returns parsed as description text
   (get_stock_fundamentals)

5. Missing blank line between Args and Returns sections
   (google_search_and_scrape)

6. Return type mismatch between docstring (list) and type hint (dict)
   (google_search_and_scrape)

All 11 @tool-decorated functions now follow a consistent format:
- Summary on the opening line (no blank line after triple quotes)
- 4-space indented Args section with (type) annotations
- 4-space indented Returns section
- Blank line separating each section
- No extraneous sections (Note, Keys) that confuse the parser